Agents: document MCP client and server elicitation#31974
Merged
Conversation
mattzcarey
requested review from
a team,
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
as code owners
Contributor
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
github-actions
Bot
added
product:changelog
product:agents
github-actions
Bot
assigned
elithrar,
irvinebroque,
rita3ko,
thomasgauvin,
threepointone and
whoiskatrin
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
irvinebroque
approved these changes
Jul 11, 2026
irvinebroque
left a comment
irvinebroque
left a comment
Contributor
There was a problem hiding this comment.
How about taking the mermaid diagram from here and using to convey this flow in changelog?
https://modelcontextprotocol.io/specification/draft/client/elicitation
Stamp so you have it, see comments
…elog - New Elicitation section in the McpClient API docs: onElicitRequest, handler-driven capability advertisement (form+url with an override, form-only without), explicit capability narrowing, and the broadcast/respond pattern for forwarding elicitation to a UI - Cross-link from the server-side elicitInput docs - Changelog: URL elicitations are in the Agents SDK
mattzcarey
force-pushed
the
docs/agents-url-elicitation
branch
from
f3529f6 to
31819a0
Compare
mattzcarey
changed the title
Document form and URL modes against MCP 2025-11-25, correct consent and completion semantics, add server and client implementation guidance, and publish the changelog on the release date.
mattzcarey
force-pushed
the
docs/agents-url-elicitation
branch
from
31819a0 to
eac97f9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents MCP elicitation support in the Agents SDK for the
agents@0.17.4release.configureElicitationHandlers({ form, url })inonStart()for Agents acting as MCP clientselicitInput()examplesmcp-clientandmcp-elicitationexamplesThe docs intentionally cover the supported Agent client API only. They do not promise a public lower-level
MCPClientConnectionAPI.Verification
pnpm run format:core:checkpnpm run checkDocumentation checklist